Method and system for optimizing live migration of persistent data of virtual machine using disk i/o heuristics

ABSTRACT

Techniques for migrating persistent data between and across data stores are implemented using monitoring methods. The method includes classifying frequently updated blocks of persistent data to distinguish those blocks from less frequently updated blocks of persistent data. The less frequently updated blocks are copied from the source data store to the destination data store, such that persistent data is copied to the destination data store in the absence of the persistent data of the frequently updated blocks. The method further includes identifying a modified set of the less frequently updated blocks that are modified during the copying. The modified set of less frequently updated blocks is copied from the source data store to the destination data store, without copying the frequently updated blocks. It is then determined whether to copy the frequently updated blocks of persistent data from the source data store to the destination data store.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation which claims the benefit of U.S. patent application Ser. No. 12/881,992, filed Sep. 14, 2010 (now issued U.S. Pat. No. 8,386,731), which claims the benefit of U.S. Provisional Patent Applications Ser. Nos. 61/242,360 and 61/242,340, both filed Sep. 14, 2009. The entire contents of these applications are incorporated by reference herein.

BACKGROUND

In a process known as live migration of virtual machines (VMs), a VM's runtime state can be moved without disruption or downtime to a different physical host. Live migration of VMs is essential for increasing the mobility of virtual machines and improving resource utilization in a data center. In addition, techniques have been developed for system administrators to migrate persistent data of a VM, e.g., its virtual disks, between or across data stores with no significant disruption or downtime. This enables efficient and flexible storage management in a virtual infrastructure, such as array migration, storage upgrade, and dynamic optimization of storage performance.

One technique for migrating persistent data of a VM between or across data stores with very little disruption or downtime is described in U.S. patent application Ser. No. 12/184,134, filed Feb. 9, 2009 and entitled, “Online Virtual Machine Disk Migration,” the entire contents of which is incorporated by reference herein. In this technique, redo logs are employed to store copies of those blocks of a VM's persistent data that have changed while the migration process is being carried out iteratively. Each redo log stores copies of the changed blocks during one iteration of the migration process and is copied over to the destination at the end of the iteration. The migration process is completed by pausing the VM and merging the redo logs at the destination with an initial copy of the VM' s persistent data that was created at the destination at the beginning of the migration process.

One of the drawbacks of the redo log approach is that the virtual machine whose persistent data is being migrated uses two different data stores to store its persistent data while the process is ongoing. This is undesirable because relying on two data stores increases vulnerability of the virtual machine during data migration in that a crash of either the source data store or the destination data store will become a failure condition.

Another drawback of the redo log approach is the size of the redo logs. If the VM has a lot of write activity during the migration process, the redo logs can become quite large in size and consume extra storage capacity. Further, if the redo logs are large in size, the final step of merging the redo logs with the initial copy of the VM's persistent data, which is carried out while the VM is paused, may take too long and result in VM downtime.

SUMMARY

Techniques for migrating persistent data of virtual machines between and across data stores are implemented using monitoring methods. The method includes classifying frequently updated blocks of persistent data to distinguish those blocks from less frequently updated blocks of persistent data. The less frequently updated blocks of persistent data are copied from the source data store to the destination data store, such that the persistent data is copied to the destination data store in the absence of the persistent data of the frequently updated blocks. The method further includes identifying a modified set of the less frequently updated blocks that are modified during the copying. The modified set of less frequently updated blocks of persistent data is copied from the source data store to the destination data store, without copying the frequently updated blocks. It is then determined whether to copy the frequently updated blocks of persistent data from the source data store to the destination data store.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a virtualized computer system in which one or more embodiments of the present invention may be practiced.

FIG. 2 depicts one example of a computer system having a virtual machine and source and destination data stores between which a process of migrating persistent VM data according to one or more embodiments of the present invention are carried out.

FIG. 3 is a flow diagram that illustrates the process of migrating persistent VM data from a source data store to a destination data store using the computer system of FIG. 2.

FIG. 4 schematically illustrates the correspondence between a virtual disk and a bitmap data structure that is used in one or more embodiments of the present invention.

FIGS. 5A and 5B illustrate the benefits of using an incremental change block tracking bitmap according to in one or more embodiments of the present invention.

FIG. 6 depicts another example of a computer system having a virtual machine and source and destination data stores between which a process of migrating persistent VM data according to one or more embodiments of the present invention are carried out.

FIG. 7 is a flow diagram that illustrates the process of migrating persistent VM data from a source data store to a destination data store using the computer system of FIG. 6.

FIG. 8 is a conceptual illustration of a change block tracking map that shows the number of times a dirty block was rewritten.

FIG. 9 illustrates a multi-stage filter implemented in one or more embodiments of the present invention.

FIG. 10 illustrates four large blocks each made up of four normal size blocks.

DETAILED DESCRIPTION

FIG. 1 depicts a block diagram of a virtualized computer system in which one or more embodiments of the present invention may be practiced. Computer system 150 may be constructed on a conventional server-class, hardware platform 152 including host bus adapters (HBA) 154 in addition to conventional platform processor, memory, and other standard peripheral components (not shown). Hardware platform 152 may be coupled to an enterprise-class storage system 182. Examples of storage system 182 may be a network attached storage (NAS) device, storage area network (SAN) arrays, or any other similar disk arrays known to those with ordinary skill in the art. In a typical implementation, there may be multiple computer systems similar to computer system 150 connected via a network fabric to multiple storage systems similar to storage system 182.

VMkernel 156 is installed on hardware platform 152 and supports virtual machine execution space 158 within which multiple VMs 160 ₁-160 _(N) may be concurrently instantiated and executed. Each such virtual machine 160 ₁-160 _(N) implements a virtual hardware (HW) platform 162 that supports the installation of a guest operating system 164 which is capable of executing applications 166. Similar to guest operating system 130, examples of guest operating system 164 may be Microsoft Windows, Linux, Solaris x86, NetWare, FreeBSD or any other operating system supported by the virtualization software. In each instance, guest operating system 164 includes a native file system layer (not shown), for example, either an NTFS or an ext3 type file system layer. The native file system layer interfaces with virtual hardware platform 162 to access, from the perspective of guest operating system 164, a data storage HBA, which in reality, is virtual HBA 168 implemented by VMM 172 that emulates virtual disks 170 _(A)-170 _(X). The virtualization of disk storage is therefore transparent to guest operating system 164, which accesses virtual disk 170 _(X) as it would any physical storage device.

Virtual machines maintain state information, some of which is volatile and would be lost upon crash of the virtual machine, and some of which is non-volatile, or persistent, which survives failure of either the virtual machine or its physical host. Storage devices for maintaining persistent state information include non-volatile RAM (NVRAM), flash drives, ordinary hard disks, RAID storage devices, and storage arrays. In a VM, persistent state information includes static data and dynamic data. As used herein, “static data” include configuration data and other data that change infrequently while the VM is running, and “dynamic data” include data that change more frequently while the VM is running based on activities of the guest operating system and the guest applications, such as one or more virtual disks and swap files.

FIG. 2 depicts a computer system having a virtual machine and source and destination data stores between which a process of migrating persistent VM data according to one or more embodiments of the present invention are carried out. FIG. 3 is a flow diagram that illustrates the process of migrating persistent VM data from a source data store to a destination data store in accordance with one or more embodiments of the present invention. In the example provided herein, a system administrator or automated system may perform migration of dynamic persistent data 256-1 from a source data store 280-1 to a destination data store 280-2 and static persistent data 268-1 from source data store 280-1 to destination data store 280-2. Live migration logic 252 orchestrates the process of migrating the persistent data of a VM 208. In one embodiment, live migration logic 252 may be a program or software component that executes in the VMkernel space of hypervisor 228, and is under control of the system administrator through a virtualized infrastructure management software (not shown) such as VMware's vCenter™. The virtualized infrastructure management software may be executed in a central server or alternatively, in a virtual machine running in a different host or in computer system 200.

Referring now to FIG. 3, in step 304, live migration logic 252 begins, by copying static persistent data 268-1 from source data store 280-1 to its counterpart static persistent data 268-2 on destination data store 280-2. The static persistent data 268-1 may include NVRAM files, configuration files, snapshot information, and various logs. Static data such as file handles may be modified during this operation so that all file handles identifying persistent data on source data store 280-1 are modified to point to copies created or to be created on destination data store 280-2.

In step 306, live migration logic 252 creates a new VM 210 (shown as an empty dashed rectangle) on the same physical host as the original virtual machine whose persistent data will be migrated. In an alternative embodiment, the new VM may be created on a different physical host and, in such an embodiment, live migration of in-memory state of VM 208 to the different physical host would be carried out also.

In step 308, live migration logic 252 begins monitoring a change block tracking (CBT) filter 236 that is provided in hypervisor 228. CBT filter 236 tracks IO operations 220 executed by VM 208. CBT filter 236 also maintains one or more change block tracking (CBT) bitmaps 240 in hypervisor 228. In one embodiment, bitmap entries of 1 indicate that the corresponding blocks have been written to, while bitmap entries of 0 indicate that the corresponding blocks have not been written to. IO operations 220 are captured by VSCSI device 224 and translated into block level IO operations. CBT filter 236 examines the block level IO operations and sets the bit values of bitmap entries corresponding to any of the blocks that are being written to. CBT filter 236 also monitors memory page swaps carried out by hypervisor 228, in particular by kernel swap 232, and sets the bit values of bitmap entries corresponding to blocks of swap files 264-1 that have changed.

For simplicity, a single CBT bitmap is illustrated in FIG. 2. In some embodiments, there may be multiple bitmaps, each allocated to a different type of dynamic persistent data 256-1. For example, there may be one bitmap for each virtual disk 260-1 and one bitmap for each instance of swap file 264-1.

In step 312, live migration logic 252 copies all dynamic persistent data 256-1, including virtual disks 260-1 and swap files 264-1, from source data store 280-1 to destination data store 280-2.

In step 316, after step 312 has been carried out, live migration logic 252 queries CBT filter 236 to determine what dynamic persistent data has changed since the cloning began. In response to the query, CBT filter 236 consults CBT bitmap 240, identifies blocks of the dynamic persistent data that changed since CBT filter 236 was last queried, and clears the bit entries corresponding to such blocks. If, in step 320, live migration logic 252 determines that the number of changed blocks in CBT bitmap 240 has fallen below a threshold, the process proceeds to step 328, where VM 208 is paused for the duration of time needed to copy these last changed blocks. The threshold is set to be low enough so that the amount of time it would take to copy the last changed blocks does not result in VM downtime that is noticeable to the users. The threshold may be predetermined, user selectable, or dynamically adjusted based on operating conditions. In one embodiment, the threshold is set based on the data throughput of the copy operation. The faster the throughput, the larger the threshold can be set such that the remaining data can be transferred without noticeable impact on the VM.

If, in step 320, live migration logic 252 determines that the number of changed blocks exceeds a threshold, the process proceeds to step 324, where live migration logic 252 copies the blocks of dynamic persistent data that have changed (since the last copy iteration) to the destination data store. After step 324, the process returns to step 316, where CBT filter 236 will be queried again for any new changes to blocks. With each iteration of this cycle, the number of changes to the blocks should be reduced, eventually to the point where the number of changed blocks is smaller than the threshold tested in step 320. Once the threshold is reached, the process proceeds to step 328.

In step 328, VM 208 is paused to prevent any new updates to the dynamic persistent data 256-1. During this paused period, VM 208 is not running applications 212 and not servicing any requests. This period of unavailability can be controlled and reduced to a level that is not discernable to users of VM 208 by waiting until the number of changes indicated in CBT bitmap 240 falls below a predetermined threshold as explained above.

Steps 332 and 336 are carried out while VM 208 is paused. In step 332, the in-memory state of the original VM 208 is migrated to new VM 210. More specifically, when VM 208 is deemed ready to be resumed, live migration logic 252 will cause the transfer the in-memory and device states to new VM 210. In one embodiment, known as fast suspend/resume, ownership of memory is transferred to new VM 210, avoiding the overhead of actually copying the memory, which would double the amount of memory consumed. In particular, following the pausing of VM 208, the state of devices emulated in VM 208, except for that VM' s memory, is serialized and stored. Metadata that hypervisor 228 is maintaining for pages of virtual memory space allocated for VM 208 are copied and used as metadata for pages of virtual memory space allocated for new VM 210. The state of emulated devices stored earlier is read out, de-serialized and loaded into corresponding devices emulated in new VM 210. New VM 210 then resumes executing guest instructions that were running inside VM 208. The fast suspend/resume process is described in further detail in U.S. patent application Ser. No. 12/559,489, entitled “Method of Suspending and Resuming Virtual Machines”, filed Sep. 14, 2009, the entire contents of which are incorporated by reference herein. As explained in that patent application, using this fast suspend/resume operation allows the VM to change configuration parameters, such as file handles that identify the location of persistent data to be changed without any downtime of the VM.

In another embodiment, a complete second copy of the original virtual machine is made, including the in-memory and device states and the set of file handles that are pointing to the persistent data on source data store 280-1. In further embodiments, a new VM process, e.g., new VM 210, need not be initialized and therefore step 306 is not carried out. In such embodiments, VM 208 undergoes a normal suspend and resume or stun and unstun, such that the prior to suspend/stun VM 208 have a set of file handles that point to the persistent data on source data store 280-1 but after resume/unstun VM 208 have a set of file handles that point to the persistent data on destination data store 280-2.

In step 336, live migration logic 252 copies the last set of changed dynamic persistent data to destination data store 280-2.

In step 340, execution of the VM is resumed with all file handles now pointing to the persistent data on destination data store 280-2. Thus, all new IOs will be made to destination data store 280-2. In embodiments using new VM 210, live migration logic 252 deactivates VM 208. It should be recognized that the entire process is carried out transparently to the applications running on the guest operating system.

Finally, in step 344, live migration logic 252 causes the deletion of all the files associated with VM 208 at source data store 208-1.

FIG. 4 schematically illustrates the correspondence between a virtual disk and a bitmap data structure that is used in one or more embodiments of the present invention. More specifically, virtual disk 404, which is an example of dynamic persistent data, consists of n blocks of storage on some data store. The figure shows only a manageable handful of blocks that can be easily depicted. CBT bitmap 408 is a linear array of n bits, a compact representation of the blocks making up virtual disk 404. In some embodiments, this bitmap may be indexed starting typically at index 0 and ending at index n-1. For each block in virtual disk 404, there is a corresponding entry in the CBT bitmap 408. In the figure, a line connects index 0 of the CBT 408 with a block in virtual disk 404 just to show the correspondence. Similarly, a line connects entry at index 2 of CBT bitmap 408 with this corresponding block in virtual disk 404, and so on for the entry at index 9 in CBT bitmap 408. When a bit at some index is set to 1, this means that the corresponding block in virtual disk 404 has been modified; similarly, when a bit at some index is set to zero, this means that the corresponding block in virtual disk 404 has not been modified. For example, note that at index 0, the bit is set to 1, indicating that the corresponding block in virtual disk 404 is dirty. To emphasize pictorially that a block is dirty in virtual disk 404 the block is crosshatched; this block is indicated by dirty blocks 412. The corresponding entry in the CBT bitmap 408 is also crosshatched just to make it easier to see that the bit is set to 1. Again, note that the indices of this bitmap, which is represented as an array of n bits, begin at 0 and are shown as increasing monotonically to the right ending at index n-1; this is merely for illustrative purposes and should not be construed as limiting the scope of the invention. What is required is that each entry in the bitmap is uniquely identified by some index that makes it possible to access that bitmap entry quickly.

One technique for optimizing the process of migrating persistent VM data is to employ an incremental CBT bitmap. FIG. 5A and FIG. 5B illustrates the differences between CBT bitmap 504 and incremental CBT bitmap 524. Both FIG. 5A and FIG. 5B illustrate the state of the CBT bitmap while a copy operation (e.g., steps 312 and 324) is being performed. As described above, in step 312, the copy operation is performed on all blocks corresponding to bitmap entries 0 through n-1, and in step 324, the copy operation is performed on those blocks corresponding to bitmap entries 0 through n-1 that have been dirtied. Arrow 508 indicates the progress of the copy operation.

As shown in FIG. 5A, CBT bitmap 504 tracks dirtied blocks so long as they were dirtied after TIME=t0. For example, at TIME=t1, bitmap entries 5 and 9 are set to 1 indicating that the blocks corresponding to these bitmap entries have been dirtied between TIME=t0 and TIME=t1. As a result, such blocks will end up being copied twice—once between TIME=t1 and TIME=tf and another time during a subsequent iteration because these blocks would be indicated by CBT bitmap 504 as being dirtied.

On the other hand, if an incremental CBT bitmap is used, blocks corresponding to bitmap entries 5 and 9 will be copied only once in the above example. This is achieved in one or more embodiments of the present invention by modifying CBT filter 236 so that it sets the bitmap entries corresponding to dirtied blocks based on whether or not a copy operation has progressed past those blocks. With the modification, CBT filter 236 examines the progress of a copy operation during either step 312 or 324 and while this copy operation is being carried out, sets the bitmap entries corresponding to dirtied blocks if the copy operation has progressed past those blocks and does not set the bitmap entries corresponding to dirtied blocks if the copy operation has not yet progressed past those blocks. Experimental results have shown that the use of an incremental CBT bitmap reduces the number of dirty blocks by about 81% for the initial copy (step 312).

In FIG. 5B, where arrow 508 indicates the progress of the copy operation, the modified CBT filter 236 would have set bitmap entries 1 and 3 when TIME reaches t1 because the blocks corresponding to these bitmap entries have been dirtied between TIME=t0 and TIME=t1 and the copy operation has progressed past those blocks. However, the modified CBT filter 236 would not have set bitmap entries 5 and 9 when TIME reaches t1 even though the blocks corresponding to these bitmap entries have been dirtied between TIME=t0 and TIME=t1, because the copy operation has not progressed past those blocks.

In one or more embodiments of the present invention, a Bloom filter may be used in place of CBT bitmaps as a more space-efficient data structure for keeping track of dirtied blocks. One such embodiment is shown in FIG. 6, where a Bloom filter module 636 replaces CBT filter 236 and Bloom filter 640 replaces CBT bitmap 240, and live migration logic 652 is modified to use Bloom filter 640 to keep track of dirtied blocks. Bloom filter 640 is a bit array of m bits and is associated with k different hash functions, where m and k are user configurable and may be adjusted up or down depending on particular use cases. When a write IO operation is executed by VM 208, Bloom filter module 636 calculates k different hash results by hashing the block address of the write IO operation using the k different hash functions and sets the bits in the Bloom filter 640 at bit positions corresponding to the k different hash results to 1. To query whether a particular block has been dirtied or not, the address of the particular block is hashed using the k different hash functions and the bit positions in the Bloom filter 640 corresponding to the hash results are examined. If all of the bit positions have bit values of 1, it is determined that the particular block has been dirtied.

FIG. 7 is a flow diagram that illustrates the process of migrating persistent VM data using a Bloom filter. Steps 704 and 706 are the same as steps 304 and 306. In Step 708, live migration logic 652 begins monitoring of Bloom filter module 636 which updates Bloom filter 640, in the manner described above, each time a write IO operation is executed by VM 208. Bloom filter module 636 also tracks memory page swaps carried out by hypervisor 228, in particular by kernel swap 232, and updates Bloom filter 640 using addresses of blocks of swap files 264-1 that have changed.

In step 712, live migration logic 652 copies all dynamic persistent data 256-1, including virtual disks 260-1 and swap files 264-1, from source data store 280-1 to destination data store 280-2.

In step 716, after step 712 has been carried out, live migration logic 652 queries Bloom filter module 636 to determine what dynamic persistent data has changed since the copying began. In response to the query, Bloom filter module 636 calculates k different hash results for each block address of virtual disks 260-1 and swap files 264 to identify those blocks that have been dirtied since the last query. If, in step 720, live migration logic 652 determines that the number of dirtied blocks has fallen below a threshold, the process proceeds to step 728. Steps 728, 732, 736, 740, and 744 are carried out in the same manner as Steps 328, 332, 336, 340, and 344.

If, in step 720, live migration logic 652 determines that the number of dirtied blocks exceeds a threshold, the process proceeds to step 724, where live migration logic 652 copies the blocks of dynamic persistent data that have changed (since the last copy iteration) to the destination data store. After step 724, the process returns to step 716, where Bloom filter module 636 will be queried again for any new changes to blocks. With each iteration of this cycle, the number of changes to the blocks should be reduced, eventually to the point where the number of changed blocks is smaller than the threshold tested in step 720. Once the threshold is reached, the process proceeds to step 728.

One or more embodiments of the present invention employ heat-based optimization so that “hot” blocks, i.e., blocks that are frequently updated, are filtered out. FIG. 8 is a conceptual illustration of a change block tracking map that shows the number of times a dirty block was rewritten. Thus, it can be observed from FIG. 8 that the first dirty block (starting from the left of the figure) was rewritten just once. The next dirty block was rewritten three times, and so on.

In order to track the “hotness” of a block, a multi-stage filter is employed in one or more embodiments of the present invention. It should be recognized that a Bloom filter may also be used. FIG. 9 illustrates an example of a multi-stage filter 900 employed in one or more embodiments of the present invention. Multi-stage filter 900 has n stages 904, and each stage has an array of m counters 908 and a uniform hash function H_(i), where 0≦i≦n. When a block is dirtied, n different hash values of the block are calculated using the hash function H_(i) and the block's address, and the counters corresponding to the n different hash values in all stages are incremented. The hotness of a block can be determined by checking the counters corresponding to the n different hash values calculated using the hash function H_(i) and the block's address. Only if all counters are greater than a threshold t, the block is considered to be hot.

Prior to the pre-copy phase of live migration 252 or 652, live migration logic 252 or 652 queries multi-stage filter 900 and does not copy the hot blocks to destination data store 280-2 until the last iteration (step 336 or step 736) when the remaining changed blocks are copied to destination data store 280-2. If the number of hot blocks is too large so that the last iteration will take too long, the threshold, t, can be adjusted upwards. In one embodiment, multi-stage filter 900 continues monitoring writes to the blocks through the pre-copy phase and subsequent copy iterations, and identifies additional hot blocks to filter and not copy during the subsequent copy iterations. In an alternative embodiment, the hot blocks identified prior to the pre-copy phase are filtered only during the pre-copy phase (step 312 or step 712). Also, the multi-stage filter may be cleared and the heat of the blocks recalculated periodically as the workload characteristic of a VM changes.

Pre-copy block coalescing is another method for optimizing the process of migrating persistent VM data. In this method, dirty blocks that are close together in CBT bitmap 240 are coalesced and transferred as one large block even though there may be one or more unmodified blocks in between. In one embodiment, the data mover residing inside VMKernel 156 is used to move the blocks from source data store 280-1 to destination data store 280-2. FIG. 10 shows four large blocks 1001, 1002, 1003, 1004, each having 4 normal size blocks. According to one or more embodiments of the present invention, each of large blocks 1001, 1003 is transferred as one large block. In the case of large block 1001, even though it is fragmented and includes one unmodified block, the efficiency gained from transferring this as one large block instead of 3 smaller blocks is likely to outweigh the extra cost of transferring one unmodified block. Under some workloads, efficiency may be gained by transferring large block 1004 as one large block as well.

Certain workloads execute write IO operations sequentially, for example, a redo log or a log file for a database. As with “hot” blocks, sequential IO streams may be detected and copying of blocks modified by such IO streams may be deferred until the final copy iteration. The amount of data that can be skipped may be calculated based on history or some well-known heuristic. In one embodiment, a sequential stream filter is stacked on CBT filter 236 and configured to determine whether an IO stream constitute a sequential stream of writes.

In the embodiments of the present invention described above, the persistent data that are migrated between and across data stores are associated with a virtual machine. In other embodiments of the present invention, the migrated persistent data may be associated with multiple virtual machines, or more generally, any disk image, such as a logical unit number (LUN), a disk volume, or a file system.

The various embodiments described herein may employ various computer-implemented operations involving data stored in computer systems. For example, these operations may require physical manipulation of physical quantities usually, though not necessarily, these quantities may take the form of electrical or magnetic signals where they, or representations of them, are capable of being stored, transferred, combined, compared, or otherwise manipulated. Further, such manipulations are often referred to in terms, such as producing, identifying, determining, or comparing. Any operations described herein that form part of one or more embodiments of the invention may be useful machine operations. In addition, one or more embodiments of the invention also relate to a device or an apparatus for performing these operations. The apparatus may be specially constructed for specific required purposes, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general purpose machines may be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.

The various embodiments described herein may be practiced with other computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.

One or more embodiments of the present invention may be implemented as one or more computer programs or as one or more computer program modules embodied in one or more computer readable media. The term computer readable medium refers to any data storage device that can store data which can thereafter be input to a computer system computer readable media may be based on any existing or subsequently developed technology for embodying computer programs in a manner that enables them to be read by a computer. Examples of a computer readable medium include a hard drive, network attached storage (NAS), read-only memory, random-access memory (e.g., a flash memory device), a CD (Compact Discs) CD-ROM, a CD-R, or a CD-RW, a DVD (Digital Versatile Disc), a magnetic tape, and other optical and non-optical data storage devices. The computer readable medium can also be distributed over a network coupled computer system so that the computer readable code is stored and executed in a distributed fashion.

Although one or more embodiments of the present invention have been described in some detail for clarity of understanding, it will be apparent that certain changes and modifications may be made within the scope of the claims. Accordingly, the described embodiments are to be considered as illustrative and not restrictive, and the scope of the claims is not to be limited to details given herein, but may be modified within the scope and equivalents of the claims. In the claims, elements and/or steps do not imply any particular order of operation, unless explicitly stated in the claims.

Plural instances may be provided for components, operations or structures described herein as a single instance. Finally, boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of the invention(s). In general, structures and functionality presented as separate components in exemplary configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements may fall within the scope of the appended claims(s). 

We claim:
 1. A method of migrating persistent data of a virtual machine from a source data store to a destination data store, the method comprising: classifying frequently updated blocks of persistent data to distinguish from less frequently updated blocks of persistent data; copying the less frequently updated blocks of persistent data from the source data store to the destination data store, such that the persistent data is copied to the destination data store in the absence of the persistent data of the frequently updated blocks; identifying a modified set of the less frequently updated blocks that are modified during the copying; copying the modified set of less frequently updated blocks of persistent data from the source data store to the destination data store, without copying the frequently updated blocks; and copying the frequently updated blocks of persistent data from the source data store to the destination data store after the modified set has been copied.
 2. The method of claim 1 wherein identifying the modified set and copying the modified set are repeated until determining that the number of less frequently updated blocks in the modified set is below a threshold, such that the identifying and copying is performed iteratively.
 3. The method of claim 2 wherein the frequently updated blocks are copied to the destination data store during a last copy iteration.
 4. The method of claim 3 wherein the virtual machine is paused during the last copy iteration.
 5. The method of claim 1 wherein the classifying includes: monitoring writes to each block of persistent data and deriving a write metric therefrom, designating those blocks which have a derived write metric that exceeds a threshold as being the frequently updated blocks.
 6. The method of claim 5 wherein the monitoring and the deriving are carried out using a multi-stage filter.
 7. The method of claim 5 wherein the writes to each of the blocks are monitored prior to the copying.
 8. The method of claim 5 wherein the writes to each of the blocks are monitored during the copying.
 9. The method of claim 5 wherein the monitoring and the deriving are carried out using a Bloom filter.
 10. A non-transitory computer-readable storage medium comprising computer executable instructions for executing a method of migrating persistent data of a virtual machine from a source data store to a destination data store, the method comprising: classifying frequently updated blocks of persistent data to distinguish from less frequently updated blocks of persistent data; copying the less frequently updated blocks of persistent data from the source data store to the destination data store, such that the persistent data is copied to the destination data store in the absence of the persistent data of the frequently updated blocks; identifying a modified set of the less frequently updated blocks that are modified during the copying; copying the modified set of less frequently updated blocks of persistent data from the source data store to the destination data store, without copying the frequently updated blocks; and copying the frequently updated blocks of persistent data from the source data store to the destination data store after the modified set has been copied.
 11. The computer-readable storage medium of claim 10 wherein identifying the modified set and copying the modified set are repeated until determining that the number of less frequently updated blocks in the modified set is below a threshold, such that the identifying and copying is performed iteratively.
 12. The computer-readable storage medium of claim 10 wherein the frequently updated blocks are copied to the destination data store during a last copy iteration.
 13. The computer-readable storage medium of claim 11 wherein the virtual machine is paused during the last copy iteration.
 14. The computer-readable storage medium of claim 10 wherein the classifying includes: monitoring writes to each block of persistent data and deriving a write metric therefrom, designating those blocks which have a derived write metric that exceeds a threshold as being the frequently updated blocks.
 15. The computer-readable storage medium of claim 14 wherein the monitoring and the deriving are carried out using a multi-stage filter.
 16. The computer-readable storage medium of claim 14 wherein the writes to each of the blocks are monitored prior to the copying.
 17. The computer-readable storage medium of claim 14 wherein the writes to each of the blocks are monitored during the copying.
 18. The computer-readable storage medium of claim 14 wherein the monitoring and the deriving are carried out using a Bloom filter. 